Skip to content

prov/efa: Use endpoint->peer hashmap at the AV level#11636

Merged
sunkuamzn merged 1 commit intoofiwg:mainfrom
sunkuamzn:multi-ep-av-hash
Dec 16, 2025
Merged

prov/efa: Use endpoint->peer hashmap at the AV level#11636
sunkuamzn merged 1 commit intoofiwg:mainfrom
sunkuamzn:multi-ep-av-hash

Conversation

@sunkuamzn
Copy link
Contributor

An fi_addr->peer hashmap at the endpoint level grows with the number of peers. An endpoint->peer hashmap grows with the number of endpoints - which would be better for applications that create many peers but few endpoints per AV e.g. MPI applications which
only create a single endpoint per AV.

@sunkuamzn sunkuamzn requested a review from a team November 20, 2025 18:19
@sunkuamzn
Copy link
Contributor Author

bot:aws:retest

1 similar comment
@Zhenye-Na
Copy link
Contributor

bot:aws:retest

@sunkuamzn sunkuamzn force-pushed the multi-ep-av-hash branch 3 times, most recently from f8ca132 to 4a46b73 Compare December 11, 2025 17:21
Copy link
Contributor

@shijin-aws shijin-aws left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM, thank you!

An fi_addr->peer  hashmap at the endpoint level grows
with the number of peers. An endpoint->peer hashmap
grows with the number of endpoints - which would be
better for applications that create many peers but
few endpoints per AV e.g. MPI applications which
only create a single endpoint per AV.

Signed-off-by: Sai Sunku <[email protected]>
@sunkuamzn
Copy link
Contributor Author

@j-xiong @aingerson did the vcxproj file break Intel CI?

@aingerson
Copy link
Contributor

@sunkuamzn No, we don't do any windows testing in our CI. It was a random system availability timeout. You can ignore

@sunkuamzn sunkuamzn merged commit 865ec28 into ofiwg:main Dec 16, 2025
19 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants